Problem Note 44634: SASĀ® library damage can occur if memory has been exhausted
If SAS has to acquire memory in order to process a direct access bound library, and memory has already been exhausted, error messages might occur in the SASLOG. You might see errors such as the following, which indicate that the library is damaged or that an I/O error has occurred.
ERROR: AN I/O ERROR HAS OCCURRED ON FILE libref.member.DATA.
ERROR: FILE libref.member.DATA IS DAMAGED. I/O PROCESSING DID NOT COMPLETE.
Sometimes, the following error is also written to the SASLOG:
ERROR: THE SAS SYSTEM STOPPED PROCESSING THIS STEP BECAUSE OF INSUFFICIENT MEMORY.
These messages can occur for reasons other than the scenario described in this SAS Note. If you are
running SAS® 9.3 TS1M1 or later or software releases prior to SAS®9, then you will not be affected by this problem. You might be affected if you are running SAS® 9.1 through SAS 9.3 (without the hot fix included in this note), and the error occurs while a SAS I/O is being performed.
To circumvent this problem, increase the REGION for the JOB.
Click the Hot Fix tab in this note to access the hot fix for this issue.
For SAS® 9.2 and earlier releases of SAS, contact SAS Technical Support for a special consideration ZAP.
Operating System and Release Information
SAS System | Base SAS | z/OS | 9.1 TS1M3 | 9.3 TS1M1 |
*
For software releases that are not yet generally available, the Fixed
Release is the software release in which the problem is planned to be
fixed.
If SAS has to acquire memory in order to process a direct access bound library, and memory has already been exhausted, these errors might occur:
ERROR: AN I/O ERROR HAS OCCURRED ON FILE libref.member.DATA
ERROR: FILE libref.member.DATA IS DAMAGED. I/O PROCESSING DID NOT COMPLETE.
Type: | Problem Note |
Priority: | high |
Date Modified: | 2011-11-10 08:59:21 |
Date Created: | 2011-10-12 13:51:05 |